MetadataManagerPage only supported list + delete. This adds full CRUD, a detail page, custom actions, role-based permissions, and the registry extensions needed to drive them.

Registry extensions (metadataTypeRegistry.ts)

• New MetadataFormFieldDef type and formFields property on MetadataTypeConfig — standardizes create/edit form structure per type
• New detailComponent property for custom detail renderers
• New MetadataActionDef type and actions property for custom page-level and row-level action buttons (with scope: 'page' | 'row', variant, icon, handler)
• DEFAULT_FORM_FIELDS constant (name, label, description) as fallback
• formFields populated for dashboard, page, report entries

MetadataFormDialog (components/MetadataFormDialog.tsx)

• Generic create/edit dialog driven by registry formFields
• Supports text, textarea, select field types
• Required validation, disabledOnEdit for immutable keys (e.g. name), loading state during submission

<MetadataFormDialog
  open={formOpen}
  onOpenChange={setFormOpen}
  mode="edit"
  typeLabel={config.label}
  formFields={config.formFields}
  initialValues={item}
  onSubmit={handleSave}
/>

MetadataManagerPage enhancements

• Create: "New {Type}" button in header opens create dialog
• Edit: Per-item edit button opens pre-filled edit dialog
• Navigate: Card click navigates to detail page
• Custom actions: Page-level actions rendered in header; row-level actions rendered per item card
• Permissions: Create/edit/delete buttons hidden for non-admin users via useAuth() role check
• All mutations via MetadataService.saveMetadataItem() with toast feedback, loading state, list refresh

MetadataDetailPage (pages/system/MetadataDetailPage.tsx)

• Route: /system/metadata/:metadataType/:itemName (added to all 3 route blocks)
• Displays item fields from registry config, edit via MetadataFormDialog
• Supports custom renderers via detailComponent in registry
• Permissions: Edit button hidden for non-admin users via useAuth() role check

Permission integration

• Both MetadataManagerPage and MetadataDetailPage use useAuth() from @object-ui/auth to check user.role === 'admin'
• Create, edit, and delete buttons are hidden for non-admin users
• Matches the pattern used by UserManagementPage, RoleManagementPage, and other system pages

Tests

• 38 new tests across 4 files (MetadataFormDialog: 15, MetadataDetailPage: 8, MetadataManagerPage: 8 new, metadataTypeRegistry: 7 new)
• All 62 metadata-related tests pass